Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f170f69413833dbdcc88c72c9dcc516401c46c9e6f32bdefa2e725c5900b305f

Tx prefix hash: 6071a6162b6556a790b391307c29ea93b212a85755d51d444843150972da1030
Tx public key: 3983e3c0b6d6d2535c6b72b4705b0b702f20bcb43c4f46daa2c0467d2ab7771c
Timestamp: 1731284636 Timestamp [UCT]: 2024-11-11 00:23:56 Age [y:d:h:m:s]: 00:185:14:14:13
Block: 1151029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132492 RingCT/type: yes/0
Extra: 013983e3c0b6d6d2535c6b72b4705b0b702f20bcb43c4f46daa2c0467d2ab7771c021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4c9b1b74c98ba85fac4bdee4534d4daf70341463910746e750a1faf28050904 0.600000000000 1636480 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": 1151039, "vin": [ { "gen": { "height": 1151029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4c9b1b74c98ba85fac4bdee4534d4daf70341463910746e750a1faf28050904" } } ], "extra": [ 1, 57, 131, 227, 192, 182, 214, 210, 83, 92, 107, 114, 180, 112, 91, 11, 112, 47, 32, 188, 180, 60, 79, 70, 218, 162, 192, 70, 125, 42, 183, 119, 28, 2, 17, 0, 0, 0, 2, 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