Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ebad9210330bda29c69b489ec6a8f9b421a60450acfd182e1f52f0f011b7de5

Tx prefix hash: 523290df2c59cc463a513055b98c20a0203f38680690dc4463638eed5e86c6e3
Tx public key: 04c1ee32f8fa5ed077141243b5648ce66c1032c24fad89f0a63e58db3dad29b0
Timestamp: 1638184947 Timestamp [UCT]: 2021-11-29 11:22:27 Age [y:d:h:m:s]: 03:168:17:46:40
Block: 384636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 899299 RingCT/type: yes/0
Extra: 0104c1ee32f8fa5ed077141243b5648ce66c1032c24fad89f0a63e58db3dad29b0021100000041e9564d6f000000000000000000

1 output(s) for total of 32.625082594000 dcy

stealth address amount amount idx
00: f7d11efde9cf5d1918d5dee314c1532f2535f53515280df37c0f7008db373a17 32.625082594000 776297 of 0

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": 384646, "vin": [ { "gen": { "height": 384636 } } ], "vout": [ { "amount": 32625082594, "target": { "key": "f7d11efde9cf5d1918d5dee314c1532f2535f53515280df37c0f7008db373a17" } } ], "extra": [ 1, 4, 193, 238, 50, 248, 250, 94, 208, 119, 20, 18, 67, 181, 100, 140, 230, 108, 16, 50, 194, 79, 173, 137, 240, 166, 62, 88, 219, 61, 173, 41, 176, 2, 17, 0, 0, 0, 65, 233, 86, 77, 111, 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