Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52cf6a7bcd6c62828a6b227e8bc450825ee61a49fb653815ed35391bf6bf8cb1

Tx prefix hash: 31f0bfa2d35e5bffb66f3ae9af0670f3d49efa807f78251473bb51ed6babe8e2
Tx public key: 476826e42f28deaa5e904f23ce7bb2e64fe9f514b90b73149da24c0d255a310f
Timestamp: 1745533146 Timestamp [UCT]: 2025-04-24 22:19:06 Age [y:d:h:m:s]: 00:210:13:00:19
Block: 1268726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148187 RingCT/type: yes/0
Extra: 01476826e42f28deaa5e904f23ce7bb2e64fe9f514b90b73149da24c0d255a310f021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c208cbe3e4c2b1d4902020bb73154e149a7b901cbcaaedd2029df36892aad3a7 0.600000000000 1755957 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": 1268736, "vin": [ { "gen": { "height": 1268726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c208cbe3e4c2b1d4902020bb73154e149a7b901cbcaaedd2029df36892aad3a7" } } ], "extra": [ 1, 71, 104, 38, 228, 47, 40, 222, 170, 94, 144, 79, 35, 206, 123, 178, 230, 79, 233, 245, 20, 185, 11, 115, 20, 157, 162, 76, 13, 37, 90, 49, 15, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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