Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c93951fe299a139232ef72df98dfcf56ebfcc6cb4cb729cf61f1531be0992bc

Tx prefix hash: 376259b7ba58c4186415a746be2518b325c0c59b100a967c6d21d4034191bd87
Tx public key: 54b8251781121c14a20c0e5a3186ef7fc68db67798d0cc4c267652c7d7dc39b9
Timestamp: 1736496802 Timestamp [UCT]: 2025-01-10 08:13:22 Age [y:d:h:m:s]: 00:114:01:23:03
Block: 1194175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81321 RingCT/type: yes/0
Extra: 0154b8251781121c14a20c0e5a3186ef7fc68db67798d0cc4c267652c7d7dc39b90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6144ba6bc9bac1a4942d67fb4af6318e88e397d0393c06e6a8b80f9d95d5394 0.600000000000 1680742 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": 1194185, "vin": [ { "gen": { "height": 1194175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6144ba6bc9bac1a4942d67fb4af6318e88e397d0393c06e6a8b80f9d95d5394" } } ], "extra": [ 1, 84, 184, 37, 23, 129, 18, 28, 20, 162, 12, 14, 90, 49, 134, 239, 127, 198, 141, 182, 119, 152, 208, 204, 76, 38, 118, 82, 199, 215, 220, 57, 185, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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