Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd00e41a03d0022dd78e7628e0805186807887f916050731809cabd53f512f16

Tx prefix hash: 88385b268a1fbfe56bb6eb3ec3dbb20510f5128ba7ea141295e968152567dc3d
Tx public key: 63851e8dd27b26966eaf1ddcd3ff6a0e3faa7c4a67a98fb782c7052e78cac4de
Timestamp: 1729468625 Timestamp [UCT]: 2024-10-20 23:57:05 Age [y:d:h:m:s]: 00:213:02:25:14
Block: 1136027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152151 RingCT/type: yes/0
Extra: 0163851e8dd27b26966eaf1ddcd3ff6a0e3faa7c4a67a98fb782c7052e78cac4de021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c81ced1de0b9baf0c9ff4135855282268ed9bcd0961eee7a01e72e5d8804f7d 0.600000000000 1619368 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": 1136037, "vin": [ { "gen": { "height": 1136027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c81ced1de0b9baf0c9ff4135855282268ed9bcd0961eee7a01e72e5d8804f7d" } } ], "extra": [ 1, 99, 133, 30, 141, 210, 123, 38, 150, 110, 175, 29, 220, 211, 255, 106, 14, 63, 170, 124, 74, 103, 169, 143, 183, 130, 199, 5, 46, 120, 202, 196, 222, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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