Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dab5664a53cf16d8c98d0fe7104075d1146ff1565d1d971ebb16fb2b0e9e1fd

Tx prefix hash: 97b91624424a2019dbb20c68dfadc7a63259565911dcd0ff543ae83de7759060
Tx public key: 07c4d1e436af5a62c6f005cee1684f314f5380456ff7a6a04f00038a2d01213c
Timestamp: 1720195372 Timestamp [UCT]: 2024-07-05 16:02:52 Age [y:d:h:m:s]: 00:318:01:43:55
Block: 1059168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227303 RingCT/type: yes/0
Extra: 0107c4d1e436af5a62c6f005cee1684f314f5380456ff7a6a04f00038a2d01213c02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dbb74b801b5b01972fd5a9a0d7de139fbd2dbcc08c565a4149684ea722d3298 0.600000000000 1529631 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": 1059178, "vin": [ { "gen": { "height": 1059168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dbb74b801b5b01972fd5a9a0d7de139fbd2dbcc08c565a4149684ea722d3298" } } ], "extra": [ 1, 7, 196, 209, 228, 54, 175, 90, 98, 198, 240, 5, 206, 225, 104, 79, 49, 79, 83, 128, 69, 111, 247, 166, 160, 79, 0, 3, 138, 45, 1, 33, 60, 2, 17, 0, 0, 0, 6, 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