Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6682f2147e8fd06cc5fa75d1a15f68e6b27521bcb8796a7a55670aed5712cba

Tx prefix hash: ee1709cdfe1c8c393994ba5f413a8694bb2a25576e1ece2752791652f4b57a14
Tx public key: 706d3cdd26f6ce91023570720c3c1f1c96f419993dd619cafaa70e53ab2773a4
Timestamp: 1706928746 Timestamp [UCT]: 2024-02-03 02:52:26 Age [y:d:h:m:s]: 01:293:15:50:56
Block: 949173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468672 RingCT/type: yes/0
Extra: 01706d3cdd26f6ce91023570720c3c1f1c96f419993dd619cafaa70e53ab2773a40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f0f289ee6a03cde12d5435eb1c2bd14cfdebba4e4fde72b86a866a39b87fa25 0.600000000000 1407695 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": 949183, "vin": [ { "gen": { "height": 949173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f0f289ee6a03cde12d5435eb1c2bd14cfdebba4e4fde72b86a866a39b87fa25" } } ], "extra": [ 1, 112, 109, 60, 221, 38, 246, 206, 145, 2, 53, 112, 114, 12, 60, 31, 28, 150, 244, 25, 153, 61, 214, 25, 202, 250, 167, 14, 83, 171, 39, 115, 164, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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