Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b86f4b0374b2ca8ee3b073fe20f187b8121ee5bc7d27abd27d72136122c6cbd

Tx prefix hash: 0cba9306ed896fc2b511c9312cb6ea450927bb058cf0f533fa6e70dd7b3effb2
Tx public key: 088981ef22ee59285f1cca2dc3f13bbcec8dd066149cf1a226c1b398b3dfa98d
Timestamp: 1720244041 Timestamp [UCT]: 2024-07-06 05:34:01 Age [y:d:h:m:s]: 00:251:19:21:38
Block: 1059577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179919 RingCT/type: yes/0
Extra: 01088981ef22ee59285f1cca2dc3f13bbcec8dd066149cf1a226c1b398b3dfa98d0211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee101afe9abb6253521eeccb16f9c5b9ee649853a0886fd93870fec541137c5e 0.600000000000 1530046 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": 1059587, "vin": [ { "gen": { "height": 1059577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee101afe9abb6253521eeccb16f9c5b9ee649853a0886fd93870fec541137c5e" } } ], "extra": [ 1, 8, 137, 129, 239, 34, 238, 89, 40, 95, 28, 202, 45, 195, 241, 59, 188, 236, 141, 208, 102, 20, 156, 241, 162, 38, 193, 179, 152, 179, 223, 169, 141, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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