Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 258d4b50d49e241965fb36da630a7ee32e4a1c496d52e4e836df8a4ffceaddc5

Tx prefix hash: 42a01cadb39509156b98d84d0bd55f0f38791b26ae3ee0b203f5d851fec6ff8c
Tx public key: 0e48112d750a1804cc0fb3baf5e0cc35266e2ec386e12d5fad6eeb0bfbcbe138
Timestamp: 1724214507 Timestamp [UCT]: 2024-08-21 04:28:27 Age [y:d:h:m:s]: 00:233:11:33:08
Block: 1092506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166740 RingCT/type: yes/0
Extra: 010e48112d750a1804cc0fb3baf5e0cc35266e2ec386e12d5fad6eeb0bfbcbe13802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f994f5b75ecaf4d64410c5b02efa287b2eb87f8cd50223f8dd1096881f2422ed 0.600000000000 1567265 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1092516, "vin": [ { "gen": { "height": 1092506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f994f5b75ecaf4d64410c5b02efa287b2eb87f8cd50223f8dd1096881f2422ed" } } ], "extra": [ 1, 14, 72, 17, 45, 117, 10, 24, 4, 204, 15, 179, 186, 245, 224, 204, 53, 38, 110, 46, 195, 134, 225, 45, 95, 173, 110, 235, 11, 251, 203, 225, 56, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8