Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c63b3a4ae38a5eb381096dc81df608dc33929dfc4b83cc6af623ed2326d9f36

Tx prefix hash: cd2f8bfea2d612615aacede8ca60e7890c5755d63d6e471e258b0b2b880cb7cc
Tx public key: 0140404c6b41021a5bd72a9dffbc7081fdacf4ad77e57acb5ff464df812ac23a
Timestamp: 1745265713 Timestamp [UCT]: 2025-04-21 20:01:53 Age [y:d:h:m:s]: 00:285:16:47:28
Block: 1266507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201827 RingCT/type: yes/0
Extra: 010140404c6b41021a5bd72a9dffbc7081fdacf4ad77e57acb5ff464df812ac23a02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bb9708e693229e5c959079e98bad309bd0aeab245a1db7cea21033c627d5dd7 0.600000000000 1753728 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": 1266517, "vin": [ { "gen": { "height": 1266507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bb9708e693229e5c959079e98bad309bd0aeab245a1db7cea21033c627d5dd7" } } ], "extra": [ 1, 1, 64, 64, 76, 107, 65, 2, 26, 91, 215, 42, 157, 255, 188, 112, 129, 253, 172, 244, 173, 119, 229, 122, 203, 95, 244, 100, 223, 129, 42, 194, 58, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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