Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 695610b08bbf1865f7cc1765c7dd3adde9ee778cd786a1b29cb8a0315ab0ce89

Tx prefix hash: c2d24f455909b67634e9bf675f0dccbae52dde32b0b00df4e17f924d0d8f09a7
Tx public key: f0e1bff07b6dde914fe3b2053e01eb1389f18e6999762be144a2df0c11373951
Timestamp: 1709406473 Timestamp [UCT]: 2024-03-02 19:07:53 Age [y:d:h:m:s]: 01:249:12:53:21
Block: 969734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437064 RingCT/type: yes/0
Extra: 01f0e1bff07b6dde914fe3b2053e01eb1389f18e6999762be144a2df0c113739510211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b9e51c70753a0e2335ea80a8dd7345d6ce089988b2fb96944a9b55d7ac0cc3c 0.600000000000 1429575 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": 969744, "vin": [ { "gen": { "height": 969734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b9e51c70753a0e2335ea80a8dd7345d6ce089988b2fb96944a9b55d7ac0cc3c" } } ], "extra": [ 1, 240, 225, 191, 240, 123, 109, 222, 145, 79, 227, 178, 5, 62, 1, 235, 19, 137, 241, 142, 105, 153, 118, 43, 225, 68, 162, 223, 12, 17, 55, 57, 81, 2, 17, 0, 0, 0, 3, 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