Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 785b88ad090b7eab72593fa1715aeb7dd0f1923ec9842769e5c95bdbb85459d5

Tx prefix hash: 1a5e10551ca1d4508e2b3c9ca4c786b1abc0466b4592cb0c163e5693270a8735
Tx public key: 69f4fe1ef59f41a8d4796d794aa72aac1edc82d1819a84a282a3a2f75698a0e0
Timestamp: 1736468626 Timestamp [UCT]: 2025-01-10 00:23:46 Age [y:d:h:m:s]: 00:304:14:20:44
Block: 1193954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215199 RingCT/type: yes/0
Extra: 0169f4fe1ef59f41a8d4796d794aa72aac1edc82d1819a84a282a3a2f75698a0e00211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40cec17802b0c362b4296e094ce0c0592e08fe562cbebb79958ebd3727fed0f3 0.600000000000 1680519 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": 1193964, "vin": [ { "gen": { "height": 1193954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40cec17802b0c362b4296e094ce0c0592e08fe562cbebb79958ebd3727fed0f3" } } ], "extra": [ 1, 105, 244, 254, 30, 245, 159, 65, 168, 212, 121, 109, 121, 74, 167, 42, 172, 30, 220, 130, 209, 129, 154, 132, 162, 130, 163, 162, 247, 86, 152, 160, 224, 2, 17, 0, 0, 0, 7, 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