Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35e9e230755fe5e0e464284b1065feee3083bfce9c34c94db4d0f8b52effce45

Tx prefix hash: 99762d9edc467f949055a76fb620d3ce69f92f96efc7ba0ec703d4c0f77b4d02
Tx public key: 2e1dcf394454805775e49742de51e94a438cbd0c404f4e8b8bc992a6b4e9adb2
Timestamp: 1726550711 Timestamp [UCT]: 2024-09-17 05:25:11 Age [y:d:h:m:s]: 01:051:21:49:56
Block: 1111860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295515 RingCT/type: yes/0
Extra: 012e1dcf394454805775e49742de51e94a438cbd0c404f4e8b8bc992a6b4e9adb202110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 666d57939d7f563f1ef2ffc1d04908453636a9ef702af20bed1593c599b76aca 0.600000000000 1590971 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": 1111870, "vin": [ { "gen": { "height": 1111860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "666d57939d7f563f1ef2ffc1d04908453636a9ef702af20bed1593c599b76aca" } } ], "extra": [ 1, 46, 29, 207, 57, 68, 84, 128, 87, 117, 228, 151, 66, 222, 81, 233, 74, 67, 140, 189, 12, 64, 79, 78, 139, 139, 201, 146, 166, 180, 233, 173, 178, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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