Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c531285df0ecabcf689c82efb86029223fc95243ab9244b2ff5a62219d3ec6a3

Tx prefix hash: 0a48b3d662f2be5fac05f32f7f1f4c7c53243b917ce93a83dc67d07fe69837d5
Tx public key: 868a4350be59aafa0ef6d21f88829c1707b0f6cf43e3922f4b8853ffb77dce9f
Timestamp: 1717287165 Timestamp [UCT]: 2024-06-02 00:12:45 Age [y:d:h:m:s]: 00:222:04:22:15
Block: 1035071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158996 RingCT/type: yes/0
Extra: 01868a4350be59aafa0ef6d21f88829c1707b0f6cf43e3922f4b8853ffb77dce9f021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a020ed4d7b78923a3f07a42a094e0979ce7dbe9681693059eeb7f006dc529c2 0.600000000000 1503590 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": 1035081, "vin": [ { "gen": { "height": 1035071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a020ed4d7b78923a3f07a42a094e0979ce7dbe9681693059eeb7f006dc529c2" } } ], "extra": [ 1, 134, 138, 67, 80, 190, 89, 170, 250, 14, 246, 210, 31, 136, 130, 156, 23, 7, 176, 246, 207, 67, 227, 146, 47, 75, 136, 83, 255, 183, 125, 206, 159, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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