Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e0dd07a1382d0dcc7338d5091c2dcbed98021eead85e306c1f29c07ce0e01aa

Tx prefix hash: c026e47bac8a27907cb93813797a889c9f26afad84be048ff25791a090473d6a
Tx public key: 108408b017edf1e0e088aee505d4aebf581cba49c372846f21835b46c2824246
Timestamp: 1723202941 Timestamp [UCT]: 2024-08-09 11:29:01 Age [y:d:h:m:s]: 00:166:07:47:02
Block: 1084114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118936 RingCT/type: yes/0
Extra: 01108408b017edf1e0e088aee505d4aebf581cba49c372846f21835b46c282424602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3f65f8481b58935232f5c173d7784691376aa073c7c6bdf065519f4c76e933a 0.600000000000 1558273 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": 1084124, "vin": [ { "gen": { "height": 1084114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3f65f8481b58935232f5c173d7784691376aa073c7c6bdf065519f4c76e933a" } } ], "extra": [ 1, 16, 132, 8, 176, 23, 237, 241, 224, 224, 136, 174, 229, 5, 212, 174, 191, 88, 28, 186, 73, 195, 114, 132, 111, 33, 131, 91, 70, 194, 130, 66, 70, 2, 17, 0, 0, 0, 9, 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