Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 722ef295adc35a87924d4c48942a52363c878e64b570eba31e6b44514827bf4f

Tx prefix hash: c475a090c1feb5d5a5ba87c46b8e408e77bb57879a2c7a767ccb366b039fb0d2
Tx public key: c27a4d1c844287207ea76da05037645e119eb56aec8e99a718c0ccb1d91d45ac
Timestamp: 1710705652 Timestamp [UCT]: 2024-03-17 20:00:52 Age [y:d:h:m:s]: 01:017:00:25:20
Block: 980524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273115 RingCT/type: yes/0
Extra: 01c27a4d1c844287207ea76da05037645e119eb56aec8e99a718c0ccb1d91d45ac02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87cc22d2b832469f92dc999c12e153e3707b8d02e1c963c84688c1aeba925c04 0.600000000000 1440597 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": 980534, "vin": [ { "gen": { "height": 980524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87cc22d2b832469f92dc999c12e153e3707b8d02e1c963c84688c1aeba925c04" } } ], "extra": [ 1, 194, 122, 77, 28, 132, 66, 135, 32, 126, 167, 109, 160, 80, 55, 100, 94, 17, 158, 181, 106, 236, 142, 153, 167, 24, 192, 204, 177, 217, 29, 69, 172, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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