Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b9cc98a4a4357ac7050ae024b4763c4aea4bc13fca400ba99f4f496a84dbf51

Tx prefix hash: 19f9ae0b35536cb6295e915c704d69240f6ed50bb3fbd13650db88ee279972c0
Tx public key: 818882b5b59b235a88d4f17a9beb2610fc0e3c8d3099e75b24af1efbe123bf7e
Timestamp: 1736896478 Timestamp [UCT]: 2025-01-14 23:14:38 Age [y:d:h:m:s]: 00:307:23:59:59
Block: 1197489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217636 RingCT/type: yes/0
Extra: 01818882b5b59b235a88d4f17a9beb2610fc0e3c8d3099e75b24af1efbe123bf7e021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18318de97759dfffe6bb0e2baaa1a3894dd40916a5574a5c820ffa21d28ebde5 0.600000000000 1684098 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": 1197499, "vin": [ { "gen": { "height": 1197489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18318de97759dfffe6bb0e2baaa1a3894dd40916a5574a5c820ffa21d28ebde5" } } ], "extra": [ 1, 129, 136, 130, 181, 181, 155, 35, 90, 136, 212, 241, 122, 155, 235, 38, 16, 252, 14, 60, 141, 48, 153, 231, 91, 36, 175, 30, 251, 225, 35, 191, 126, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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