Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d03646864190b434387a78ae470e1381b8cd070585ab9279df32dadf3b9fe6e5

Tx prefix hash: 48b3d2a6226bd9af97d19b2f5dad0e481d55d676c100bd23d0239625b048cb62
Tx public key: 475d65bb4f674d10537d39e045c37a20020d43864be666ab3b1cff8ecdfdd184
Timestamp: 1738398276 Timestamp [UCT]: 2025-02-01 08:24:36 Age [y:d:h:m:s]: 00:095:11:02:56
Block: 1209650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68291 RingCT/type: yes/0
Extra: 01475d65bb4f674d10537d39e045c37a20020d43864be666ab3b1cff8ecdfdd1840211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc9ea673dae35d9175f793f4fc4ebdca8802171f7750d3f45b18bb2d37c7df09 0.600000000000 1696395 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": 1209660, "vin": [ { "gen": { "height": 1209650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc9ea673dae35d9175f793f4fc4ebdca8802171f7750d3f45b18bb2d37c7df09" } } ], "extra": [ 1, 71, 93, 101, 187, 79, 103, 77, 16, 83, 125, 57, 224, 69, 195, 122, 32, 2, 13, 67, 134, 75, 230, 102, 171, 59, 28, 255, 142, 205, 253, 209, 132, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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