Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39ac1259593f394fe1a7786dcc7d60974168b474faa802ae40240f6e2ba89e8b

Tx prefix hash: 4153c2020da9bd3f280db0e5cab86b16e9f57183eae214b4c7be8852864c1938
Tx public key: fe41e6b69c3598e57fd6aedfe0d24513f6bd3265413c8fd9bd7e498ed17fa752
Timestamp: 1736070784 Timestamp [UCT]: 2025-01-05 09:53:04 Age [y:d:h:m:s]: 00:123:01:31:05
Block: 1190665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87750 RingCT/type: yes/0
Extra: 01fe41e6b69c3598e57fd6aedfe0d24513f6bd3265413c8fd9bd7e498ed17fa75202110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e7789f0f38a8810b4690d0735b4336cc36e8888c1f7aa1338067dd851e403e8 0.600000000000 1677182 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": 1190675, "vin": [ { "gen": { "height": 1190665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e7789f0f38a8810b4690d0735b4336cc36e8888c1f7aa1338067dd851e403e8" } } ], "extra": [ 1, 254, 65, 230, 182, 156, 53, 152, 229, 127, 214, 174, 223, 224, 210, 69, 19, 246, 189, 50, 101, 65, 60, 143, 217, 189, 126, 73, 142, 209, 127, 167, 82, 2, 17, 0, 0, 0, 11, 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