Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 684e7bc33fe5ec808dafbec4d502e6da7158cbecd8dca4f34e613e614181267a

Tx prefix hash: 105aafe4080d5e2772fc2b29dbd28560e716198ac2e3c6ddc47d2d304aa218ec
Tx public key: d3a9844714a79b40d157b887469dd680d1bbfb51cba654888a2eee28112c0ddd
Timestamp: 1739351926 Timestamp [UCT]: 2025-02-12 09:18:46 Age [y:d:h:m:s]: 00:332:04:20:48
Block: 1217562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235230 RingCT/type: yes/0
Extra: 01d3a9844714a79b40d157b887469dd680d1bbfb51cba654888a2eee28112c0ddd021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b183d1f89b0b31ef82b72b75045114a6201d2b90231ccb60b9f0ef59df2b5d13 0.600000000000 1704375 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": 1217572, "vin": [ { "gen": { "height": 1217562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b183d1f89b0b31ef82b72b75045114a6201d2b90231ccb60b9f0ef59df2b5d13" } } ], "extra": [ 1, 211, 169, 132, 71, 20, 167, 155, 64, 209, 87, 184, 135, 70, 157, 214, 128, 209, 187, 251, 81, 203, 166, 84, 136, 138, 46, 238, 40, 17, 44, 13, 221, 2, 17, 0, 0, 0, 3, 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