Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6605d40407235e7a74e1619581aa9d72b4c24104201943cb00497894ea335ec

Tx prefix hash: 0c006ea431e69ed3130796d1bc7b277902bc315b32d4823f02415a5768f33f38
Tx public key: cda2d297bbda57cf2d5374f84b324bf5b1a4c8bdea3315b6d294e816f88f2512
Timestamp: 1670836451 Timestamp [UCT]: 2022-12-12 09:14:11 Age [y:d:h:m:s]: 02:034:13:58:45
Block: 650855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546633 RingCT/type: yes/0
Extra: 01cda2d297bbda57cf2d5374f84b324bf5b1a4c8bdea3315b6d294e816f88f251202110000000252542ceb000000000000000000

1 output(s) for total of 4.280033690000 dcy

stealth address amount amount idx
00: c2268921482332b0e55fe6febc38b0028025efdc59391d0ab25f990dba0ccd13 4.280033690000 1091248 of 0

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": 650865, "vin": [ { "gen": { "height": 650855 } } ], "vout": [ { "amount": 4280033690, "target": { "key": "c2268921482332b0e55fe6febc38b0028025efdc59391d0ab25f990dba0ccd13" } } ], "extra": [ 1, 205, 162, 210, 151, 187, 218, 87, 207, 45, 83, 116, 248, 75, 50, 75, 245, 177, 164, 200, 189, 234, 51, 21, 182, 210, 148, 232, 22, 248, 143, 37, 18, 2, 17, 0, 0, 0, 2, 82, 84, 44, 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