Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec5cd9b8eb92654ca3d8ba366c3edd97968155b48cab228a5630659ef4acc60a

Tx prefix hash: 899880364c7659e50d2a9f550c9172cd107e0a331f438bfec922afa78a84554a
Tx public key: 871d9d04aed824e94aba3a9e166d111bceb59f1e2c83aff3b24a2fb76ba5f94d
Timestamp: 1732895986 Timestamp [UCT]: 2024-11-29 15:59:46 Age [y:d:h:m:s]: 00:124:11:33:45
Block: 1164372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88758 RingCT/type: yes/0
Extra: 01871d9d04aed824e94aba3a9e166d111bceb59f1e2c83aff3b24a2fb76ba5f94d02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46f758e7c9fac0244cd14a24e3e2b6387a446611f3911c2ad2b6c766d52ce332 0.600000000000 1650045 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": 1164382, "vin": [ { "gen": { "height": 1164372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46f758e7c9fac0244cd14a24e3e2b6387a446611f3911c2ad2b6c766d52ce332" } } ], "extra": [ 1, 135, 29, 157, 4, 174, 216, 36, 233, 74, 186, 58, 158, 22, 109, 17, 27, 206, 181, 159, 30, 44, 131, 175, 243, 178, 74, 47, 183, 107, 165, 249, 77, 2, 17, 0, 0, 0, 10, 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