Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02d42d720e893959aaf3ad6ac03e9616199125a389f4fbcf60fa804e75043a83

Tx prefix hash: 44c2d367a67a29db8847a422a644f28b01033d3c59651e27bd5daebf8b7720f8
Tx public key: a32d4d1ea1725e4b8c43bb96957a6fd4c383d08d362cddfd5064fd813e85dc4a
Timestamp: 1698380798 Timestamp [UCT]: 2023-10-27 04:26:38 Age [y:d:h:m:s]: 01:165:12:53:39
Block: 878542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379300 RingCT/type: yes/0
Extra: 01a32d4d1ea1725e4b8c43bb96957a6fd4c383d08d362cddfd5064fd813e85dc4a0211000000034b8f5122000000000000000000

1 output(s) for total of 0.753400092000 dcy

stealth address amount amount idx
00: 85a8a26c6a2ee35b56243875da31eee30d3c8818ca5950eb3bdab6de4e67df6b 0.753400092000 1333994 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": 878552, "vin": [ { "gen": { "height": 878542 } } ], "vout": [ { "amount": 753400092, "target": { "key": "85a8a26c6a2ee35b56243875da31eee30d3c8818ca5950eb3bdab6de4e67df6b" } } ], "extra": [ 1, 163, 45, 77, 30, 161, 114, 94, 75, 140, 67, 187, 150, 149, 122, 111, 212, 195, 131, 208, 141, 54, 44, 221, 253, 80, 100, 253, 129, 62, 133, 220, 74, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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