Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87405dc3830c9d85aa25e690dc460d775b4e0b98ddc20dfe8bd3d8d995c7eb4a

Tx prefix hash: 8353c428724b668e24432aeeb47443a1a893e7e29e7fecc8f7c3041051f627ca
Tx public key: 1b3c2d8d80102d8802d23061fdd61a41f03f8b3cc5bebc422fa4a58f1ab198c3
Timestamp: 1709211323 Timestamp [UCT]: 2024-02-29 12:55:23 Age [y:d:h:m:s]: 01:045:09:26:02
Block: 968121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293443 RingCT/type: yes/0
Extra: 011b3c2d8d80102d8802d23061fdd61a41f03f8b3cc5bebc422fa4a58f1ab198c302110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d64e7ca978866d9d819f0a386e6918e2946413ddd94df935815eb6ec4cc8d4a7 0.600000000000 1427920 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": 968131, "vin": [ { "gen": { "height": 968121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d64e7ca978866d9d819f0a386e6918e2946413ddd94df935815eb6ec4cc8d4a7" } } ], "extra": [ 1, 27, 60, 45, 141, 128, 16, 45, 136, 2, 210, 48, 97, 253, 214, 26, 65, 240, 63, 139, 60, 197, 190, 188, 66, 47, 164, 165, 143, 26, 177, 152, 195, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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