Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d2df6ddd65b4cd4fc4da0d8fd09c8709944e3e2995be067bcbebc76277939c

Tx prefix hash: 73d889df5a917671e76c839240e33a0ea4980c3ad03602f0be416a51c43ae007
Tx public key: 19bdcc0b19d3b8fe5bccf272e478deaf2ca776b942d6ae61c00adf8680b1421c
Timestamp: 1708267140 Timestamp [UCT]: 2024-02-18 14:39:00 Age [y:d:h:m:s]: 01:263:12:22:46
Block: 960285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447082 RingCT/type: yes/0
Extra: 0119bdcc0b19d3b8fe5bccf272e478deaf2ca776b942d6ae61c00adf8680b1421c0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59d9bd9ac5a8ef7bbdc8a74ba090096289a36f91d614791e7120d1115cecf598 0.600000000000 1419848 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": 960295, "vin": [ { "gen": { "height": 960285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59d9bd9ac5a8ef7bbdc8a74ba090096289a36f91d614791e7120d1115cecf598" } } ], "extra": [ 1, 25, 189, 204, 11, 25, 211, 184, 254, 91, 204, 242, 114, 228, 120, 222, 175, 44, 167, 118, 185, 66, 214, 174, 97, 192, 10, 223, 134, 128, 177, 66, 28, 2, 17, 0, 0, 0, 8, 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