Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a1a9ac9f9f56749e692051f6117db0ff505389631a1ff104a9e29d8cdc1f2d2

Tx prefix hash: 94a5318c8dd09fe581b39642a6e70c2f3e4d7694439cea31c34f5663166658d0
Tx public key: b073e0337a27b85a3e8883d48627259185e973355a3318bbc680ec081aae76fd
Timestamp: 1721277822 Timestamp [UCT]: 2024-07-18 04:43:42 Age [y:d:h:m:s]: 00:221:09:17:11
Block: 1068165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158094 RingCT/type: yes/0
Extra: 01b073e0337a27b85a3e8883d48627259185e973355a3318bbc680ec081aae76fd02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5a3aa72dbdd7867f82e67f4a5169c6159dac5afc8e6cc50804e2a11b970041d 0.600000000000 1539204 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": 1068175, "vin": [ { "gen": { "height": 1068165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5a3aa72dbdd7867f82e67f4a5169c6159dac5afc8e6cc50804e2a11b970041d" } } ], "extra": [ 1, 176, 115, 224, 51, 122, 39, 184, 90, 62, 136, 131, 212, 134, 39, 37, 145, 133, 233, 115, 53, 90, 51, 24, 187, 198, 128, 236, 8, 26, 174, 118, 253, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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