Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca0062fabd2c2ee306f523481fab7637530b7ca4f29a9415af2f50265480273a

Tx prefix hash: e643a204b81fdb1f3719da3edbbcc0372ce4c7ecd001ef51cc47695c268b6b56
Tx public key: 53925c2c1bbd2bc9faa9a954422790eb32430e625bb76ce5b5fd664ec4a1bee9
Timestamp: 1717478866 Timestamp [UCT]: 2024-06-04 05:27:46 Age [y:d:h:m:s]: 00:346:18:42:30
Block: 1036664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247846 RingCT/type: yes/0
Extra: 0153925c2c1bbd2bc9faa9a954422790eb32430e625bb76ce5b5fd664ec4a1bee90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c2f34e68a4442f78101912b791b985260acefdd6c563e6384c9120aa7be6d12 0.600000000000 1505193 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": 1036674, "vin": [ { "gen": { "height": 1036664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c2f34e68a4442f78101912b791b985260acefdd6c563e6384c9120aa7be6d12" } } ], "extra": [ 1, 83, 146, 92, 44, 27, 189, 43, 201, 250, 169, 169, 84, 66, 39, 144, 235, 50, 67, 14, 98, 91, 183, 108, 229, 181, 253, 102, 78, 196, 161, 190, 233, 2, 17, 0, 0, 0, 2, 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