Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f10178f308717f04c03737c238246bee09289f6c35825cdaf5b07fc412850b5

Tx prefix hash: 3e85b0da53c081a5b302b17d72623ef6265663b64d0a5c993db93150db0f4c25
Tx public key: 9bb7033d3fcb45b5f9f77d3040e5a322c41245f45c3271ecff0ba488247c09a6
Timestamp: 1716704602 Timestamp [UCT]: 2024-05-26 06:23:22 Age [y:d:h:m:s]: 01:168:18:20:28
Block: 1030242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379204 RingCT/type: yes/0
Extra: 019bb7033d3fcb45b5f9f77d3040e5a322c41245f45c3271ecff0ba488247c09a60211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84bd22a74cfd4f2621139ab9a5dfa5a003338d6919579d70cf198402bc8a2f6d 0.600000000000 1498497 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": 1030252, "vin": [ { "gen": { "height": 1030242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84bd22a74cfd4f2621139ab9a5dfa5a003338d6919579d70cf198402bc8a2f6d" } } ], "extra": [ 1, 155, 183, 3, 61, 63, 203, 69, 181, 249, 247, 125, 48, 64, 229, 163, 34, 196, 18, 69, 244, 92, 50, 113, 236, 255, 11, 164, 136, 36, 124, 9, 166, 2, 17, 0, 0, 0, 3, 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