Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b98256ba84d714a589231f2b73b055edd4e778cca86ecf89c710c018149373a

Tx prefix hash: bb3d25bfcf5407dd1ed671e466cfcd14bd60aed5f175b0826df4634b3c4c1801
Tx public key: 786a499609d046e19f308d8f57c617e6e9b031041aba5d8ed0341b43f7c2c18c
Timestamp: 1694773280 Timestamp [UCT]: 2023-09-15 10:21:20 Age [y:d:h:m:s]: 01:130:17:45:23
Block: 848596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354720 RingCT/type: yes/0
Extra: 01786a499609d046e19f308d8f57c617e6e9b031041aba5d8ed0341b43f7c2c18c021100000004faf35c9c000000000000000000

1 output(s) for total of 0.946780363000 dcy

stealth address amount amount idx
00: ba0f0515d619aae130caa8688d7ae7a82d95469e0cb8d939e3c8d717177cceb9 0.946780363000 1302210 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": 848606, "vin": [ { "gen": { "height": 848596 } } ], "vout": [ { "amount": 946780363, "target": { "key": "ba0f0515d619aae130caa8688d7ae7a82d95469e0cb8d939e3c8d717177cceb9" } } ], "extra": [ 1, 120, 106, 73, 150, 9, 208, 70, 225, 159, 48, 141, 143, 87, 198, 23, 230, 233, 176, 49, 4, 26, 186, 93, 142, 208, 52, 27, 67, 247, 194, 193, 140, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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