Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e54cb2144165affdab85a8c5d0a144df8a7dffd2529c5a6b94574e2b665d71dd

Tx prefix hash: 837de8cfdb88c3cda6d8776a1650462227082d1a89485bdb78728c89b63c1b89
Tx public key: cfb6f6b2b367fb6e47f1971fb463db8d5d0436d4856cb45018f7aa53f1daa102
Timestamp: 1723559124 Timestamp [UCT]: 2024-08-13 14:25:24 Age [y:d:h:m:s]: 00:244:11:13:58
Block: 1087064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174604 RingCT/type: yes/0
Extra: 01cfb6f6b2b367fb6e47f1971fb463db8d5d0436d4856cb45018f7aa53f1daa10202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f110080a3113d9f408ffd62f332a22c9853425081fdc8ea0e538602e6fd90e00 0.600000000000 1561669 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": 1087074, "vin": [ { "gen": { "height": 1087064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f110080a3113d9f408ffd62f332a22c9853425081fdc8ea0e538602e6fd90e00" } } ], "extra": [ 1, 207, 182, 246, 178, 179, 103, 251, 110, 71, 241, 151, 31, 180, 99, 219, 141, 93, 4, 54, 212, 133, 108, 180, 80, 24, 247, 170, 83, 241, 218, 161, 2, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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