Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41c64c3ba70138c7a1ed1c64e9000766e3ed47f7b71fc6b811e08b06c59e32ad

Tx prefix hash: 9e63e7f91ef6322e59fc683a11a6545a40ceb9034cc76e3934f101ead9c26518
Tx public key: 7461cb156ced29f9aa2c1875f9b6a0ce2a587c00dd6122f79ec67aca862a7680
Timestamp: 1715770208 Timestamp [UCT]: 2024-05-15 10:50:08 Age [y:d:h:m:s]: 01:179:18:26:13
Block: 1022490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387079 RingCT/type: yes/0
Extra: 017461cb156ced29f9aa2c1875f9b6a0ce2a587c00dd6122f79ec67aca862a76800211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdbcb8a0ac25c37d01e7c0ec3a625dc20b70c4c0381dec20920c84274df9e55a 0.600000000000 1487109 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": 1022500, "vin": [ { "gen": { "height": 1022490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdbcb8a0ac25c37d01e7c0ec3a625dc20b70c4c0381dec20920c84274df9e55a" } } ], "extra": [ 1, 116, 97, 203, 21, 108, 237, 41, 249, 170, 44, 24, 117, 249, 182, 160, 206, 42, 88, 124, 0, 221, 97, 34, 247, 158, 198, 122, 202, 134, 42, 118, 128, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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