Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 057142541d7b672fbd8774b271e92d74572daf281e9efbab5b01491952c70c69

Tx prefix hash: 73f9f1c6fe99b9189192d0a8910baeea634a38db8c3260fa41c81663291013bc
Tx public key: cea810866202b577fd3e6f3b72e7a8907f788ccbdcf025a6244c0d81f69f33cb
Timestamp: 1702892105 Timestamp [UCT]: 2023-12-18 09:35:05 Age [y:d:h:m:s]: 01:150:04:57:14
Block: 915723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368505 RingCT/type: yes/0
Extra: 01cea810866202b577fd3e6f3b72e7a8907f788ccbdcf025a6244c0d81f69f33cb02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ca53e8dc5a3d5ea7f62c77121982b1d8e605270d82a06f58bdf0de10fa50367 0.600000000000 1373147 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": 915733, "vin": [ { "gen": { "height": 915723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ca53e8dc5a3d5ea7f62c77121982b1d8e605270d82a06f58bdf0de10fa50367" } } ], "extra": [ 1, 206, 168, 16, 134, 98, 2, 181, 119, 253, 62, 111, 59, 114, 231, 168, 144, 127, 120, 140, 203, 220, 240, 37, 166, 36, 76, 13, 129, 246, 159, 51, 203, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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