Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2e867ecec04ccfef549f1bda34ae5705fd1e726c32507c5b2a3da081ef0637

Tx prefix hash: 9e56241f712dfdb0c41c01b4fb4dcceff91f36a9583227dcc7e1e4362c2cafad
Tx public key: 7b530805767f3c6a4bf2ee532afd2a5670c357886d246397ead24397be9c9351
Timestamp: 1736717341 Timestamp [UCT]: 2025-01-12 21:29:01 Age [y:d:h:m:s]: 00:080:11:11:22
Block: 1196005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57286 RingCT/type: yes/0
Extra: 017b530805767f3c6a4bf2ee532afd2a5670c357886d246397ead24397be9c9351021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93160970fe568304f7424f76ee84a3cb485409e7d9d09822a6a34f0c18a6bf17 0.600000000000 1682602 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": 1196015, "vin": [ { "gen": { "height": 1196005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93160970fe568304f7424f76ee84a3cb485409e7d9d09822a6a34f0c18a6bf17" } } ], "extra": [ 1, 123, 83, 8, 5, 118, 127, 60, 106, 75, 242, 238, 83, 42, 253, 42, 86, 112, 195, 87, 136, 109, 36, 99, 151, 234, 210, 67, 151, 190, 156, 147, 81, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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