Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bbd97acf221678e9a4d1091f99aec7d9c3b6186a58fefaa98b10730bb1462d4

Tx prefix hash: 4813b1727e82fea941d18645b92f391b54b8eb3a327331a5bf7948fa03f14d7a
Tx public key: ff15f8850ade23e0a552bdcdb509d9430dc8cd6f1c8df1c5243c1f6d0b2983f9
Timestamp: 1744484350 Timestamp [UCT]: 2025-04-12 18:59:10 Age [y:d:h:m:s]: 00:293:08:10:05
Block: 1260037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207295 RingCT/type: yes/0
Extra: 01ff15f8850ade23e0a552bdcdb509d9430dc8cd6f1c8df1c5243c1f6d0b2983f90211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e84720dc2edb7b19d87cefd9b65cb53d2ac2d767d788078e7589316d7dc21ba1 0.600000000000 1747188 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": 1260047, "vin": [ { "gen": { "height": 1260037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e84720dc2edb7b19d87cefd9b65cb53d2ac2d767d788078e7589316d7dc21ba1" } } ], "extra": [ 1, 255, 21, 248, 133, 10, 222, 35, 224, 165, 82, 189, 205, 181, 9, 217, 67, 13, 200, 205, 111, 28, 141, 241, 197, 36, 60, 31, 109, 11, 41, 131, 249, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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