Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b3a44e63f54eac9fbe95f987c4d66ee0a308db15b49924e74e3ef7e51595a83

Tx prefix hash: 9f528d0bff135a5b955ccb8bfbfdd1b5b6b6e51615bcfdb6543ac5937f449a53
Tx public key: f16c24df2c0a1a628258a7e94f2183e689a9d0bdba905b088cccc7c486771844
Timestamp: 1715730756 Timestamp [UCT]: 2024-05-14 23:52:36 Age [y:d:h:m:s]: 00:289:18:43:49
Block: 1022163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207098 RingCT/type: yes/0
Extra: 01f16c24df2c0a1a628258a7e94f2183e689a9d0bdba905b088cccc7c48677184402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d12432d2c7f5b9685d86578c80e7b3a31bb7e92d5a652716a2dc13080f0dc6bb 0.600000000000 1486684 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": 1022173, "vin": [ { "gen": { "height": 1022163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d12432d2c7f5b9685d86578c80e7b3a31bb7e92d5a652716a2dc13080f0dc6bb" } } ], "extra": [ 1, 241, 108, 36, 223, 44, 10, 26, 98, 130, 88, 167, 233, 79, 33, 131, 230, 137, 169, 208, 189, 186, 144, 91, 8, 140, 204, 199, 196, 134, 119, 24, 68, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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