Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0372e8464177b45de919b74ad82fa22c2a62175a4a11e73b40976ddf21959cbe

Tx prefix hash: f5e83de7c02c23901219d67d0bfefd6a0d83dcbb9158110afdc84579a6ad437f
Tx public key: 1cf1bc6d9fa0f4e6a87cb3bc07b517417b54271340bb6b3c7d5934178f0995a2
Timestamp: 1707484418 Timestamp [UCT]: 2024-02-09 13:13:38 Age [y:d:h:m:s]: 00:340:16:22:22
Block: 953788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243883 RingCT/type: yes/0
Extra: 011cf1bc6d9fa0f4e6a87cb3bc07b517417b54271340bb6b3c7d5934178f0995a202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81596dbf48c039aeeca9c44209d0a5881d73e9664aeab5e1fafe53338814e88d 0.600000000000 1413042 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": 953798, "vin": [ { "gen": { "height": 953788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81596dbf48c039aeeca9c44209d0a5881d73e9664aeab5e1fafe53338814e88d" } } ], "extra": [ 1, 28, 241, 188, 109, 159, 160, 244, 230, 168, 124, 179, 188, 7, 181, 23, 65, 123, 84, 39, 19, 64, 187, 107, 60, 125, 89, 52, 23, 143, 9, 149, 162, 2, 17, 0, 0, 0, 1, 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