Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c6e78b55550f0ada71b59164fa06fef899c45cdd16b9fa3b993fa45bf22e43f

Tx prefix hash: baf5101b7b1cee1994803a0a6cd2956e0bf5365f8bc4f860ae75bec54940925c
Tx public key: 065955654238d6237cd12728afc34e7a803c7c2920e9a23a1ecdbb57c20f626d
Timestamp: 1751355888 Timestamp [UCT]: 2025-07-01 07:44:48 Age [y:d:h:m:s]: 00:132:09:33:43
Block: 1316403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92818 RingCT/type: yes/0
Extra: 01065955654238d6237cd12728afc34e7a803c7c2920e9a23a1ecdbb57c20f626d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44c77160c90a1d801e951c2aee7c1e58cb76c8a9091416d15410b028231f2c76 0.600000000000 1804062 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": 1316413, "vin": [ { "gen": { "height": 1316403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44c77160c90a1d801e951c2aee7c1e58cb76c8a9091416d15410b028231f2c76" } } ], "extra": [ 1, 6, 89, 85, 101, 66, 56, 214, 35, 124, 209, 39, 40, 175, 195, 78, 122, 128, 60, 124, 41, 32, 233, 162, 58, 30, 205, 187, 87, 194, 15, 98, 109, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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