Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df4f87244164c546811d2ef740ea981ec0697d9ad06611645fb0c29dd08883a3

Tx prefix hash: 8cbf1ef6f1fcedd5dcd87e332c61b404b343dde10ed728117a738443a089daf2
Tx public key: 9a740cb5062e2a91692e752e4772d62dcd9aa8bd4dba50294105d48912f15d87
Timestamp: 1711491721 Timestamp [UCT]: 2024-03-26 22:22:01 Age [y:d:h:m:s]: 01:066:13:26:47
Block: 987044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308561 RingCT/type: yes/0
Extra: 019a740cb5062e2a91692e752e4772d62dcd9aa8bd4dba50294105d48912f15d8702110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16e207d913588aed929872f32bbfd3fa6054d1d94bb3a56ae37140b271ab2cf7 0.600000000000 1447285 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": 987054, "vin": [ { "gen": { "height": 987044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16e207d913588aed929872f32bbfd3fa6054d1d94bb3a56ae37140b271ab2cf7" } } ], "extra": [ 1, 154, 116, 12, 181, 6, 46, 42, 145, 105, 46, 117, 46, 71, 114, 214, 45, 205, 154, 168, 189, 77, 186, 80, 41, 65, 5, 212, 137, 18, 241, 93, 135, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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