Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43612c88bfb3037bf21690e0a12a6c102f3efe6e9d9beac2724ae48b9ff508fb

Tx prefix hash: 4bcc9c9bdc0900d1ff62645697aeab2be72907f6f8d9d99183249331bebe76a6
Tx public key: 8b7d1800733ebc69d1b139feb78c4bc20762953865e0e48dcfb292a5d3719ad8
Timestamp: 1720205184 Timestamp [UCT]: 2024-07-05 18:46:24 Age [y:d:h:m:s]: 00:111:01:30:55
Block: 1059246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79527 RingCT/type: yes/0
Extra: 018b7d1800733ebc69d1b139feb78c4bc20762953865e0e48dcfb292a5d3719ad80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b306f2dbea8d6ec133298262c61c41a0e3e1cf8d91fb5754a725594b1df311d 0.600000000000 1529713 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": 1059256, "vin": [ { "gen": { "height": 1059246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b306f2dbea8d6ec133298262c61c41a0e3e1cf8d91fb5754a725594b1df311d" } } ], "extra": [ 1, 139, 125, 24, 0, 115, 62, 188, 105, 209, 177, 57, 254, 183, 140, 75, 194, 7, 98, 149, 56, 101, 224, 228, 141, 207, 178, 146, 165, 211, 113, 154, 216, 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