Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a52ce9146ed1a316c7b3618a734912f0ed277dbec2ea953f2f0f22511327123d

Tx prefix hash: a68a087965bc950f3a28a64dae9e925022f004e4203cf8071dce5006ec6cf1c9
Tx public key: 0367addb9376e4e28ff8f34e60b996c2b1fd079c8996a3d5200eb40fc3d3a413
Timestamp: 1717664149 Timestamp [UCT]: 2024-06-06 08:55:49 Age [y:d:h:m:s]: 00:219:17:39:32
Block: 1038197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157240 RingCT/type: yes/0
Extra: 010367addb9376e4e28ff8f34e60b996c2b1fd079c8996a3d5200eb40fc3d3a41302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d58ef90da85a2e0c178061a49821ae14103cac0205c4803f9144c2422c974aca 0.600000000000 1506758 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": 1038207, "vin": [ { "gen": { "height": 1038197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d58ef90da85a2e0c178061a49821ae14103cac0205c4803f9144c2422c974aca" } } ], "extra": [ 1, 3, 103, 173, 219, 147, 118, 228, 226, 143, 248, 243, 78, 96, 185, 150, 194, 177, 253, 7, 156, 137, 150, 163, 213, 32, 14, 180, 15, 195, 211, 164, 19, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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