Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fea6de295a9b84a8ddea408009db4178fc1b74a436fa631083ee364ce0218d2

Tx prefix hash: 75b2bd9ac444f65984417b3b4adf09cc6b8a9ac10902b9894e66fe97f34f3ebf
Tx public key: 34a1e79700d9586bfde234f8d191f4560c90f123ba4d1f5770e11689d9201b41
Timestamp: 1737119116 Timestamp [UCT]: 2025-01-17 13:05:16 Age [y:d:h:m:s]: 00:306:01:03:17
Block: 1199333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216237 RingCT/type: yes/0
Extra: 0134a1e79700d9586bfde234f8d191f4560c90f123ba4d1f5770e11689d9201b4102110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4dd0aac193d0df87f7e4ff40adb6e2fffbf0ef59b4009ecdb85f5eeb66610a9 0.600000000000 1685964 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": 1199343, "vin": [ { "gen": { "height": 1199333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4dd0aac193d0df87f7e4ff40adb6e2fffbf0ef59b4009ecdb85f5eeb66610a9" } } ], "extra": [ 1, 52, 161, 231, 151, 0, 217, 88, 107, 253, 226, 52, 248, 209, 145, 244, 86, 12, 144, 241, 35, 186, 77, 31, 87, 112, 225, 22, 137, 217, 32, 27, 65, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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