Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98293d4e1990e612bd4fff747d53165d61cc01f790ff7dd24cc0c6178c064f8b

Tx prefix hash: be77436ec972100ee911b47a85a3cdad745842edc4ca8fdb8fd406a8a44c8ce0
Tx public key: eb4a5660dac34a3f879f43255565d448a5f041e56d9b44313b3f6231705cea5a
Timestamp: 1721293133 Timestamp [UCT]: 2024-07-18 08:58:53 Age [y:d:h:m:s]: 00:266:16:55:07
Block: 1068292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190523 RingCT/type: yes/0
Extra: 01eb4a5660dac34a3f879f43255565d448a5f041e56d9b44313b3f6231705cea5a02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b533c8e0a0b5bc30f19e475ac965fbdbb8a6a05b24f3d314e48666ae3f625c6b 0.600000000000 1539369 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": 1068302, "vin": [ { "gen": { "height": 1068292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b533c8e0a0b5bc30f19e475ac965fbdbb8a6a05b24f3d314e48666ae3f625c6b" } } ], "extra": [ 1, 235, 74, 86, 96, 218, 195, 74, 63, 135, 159, 67, 37, 85, 101, 212, 72, 165, 240, 65, 229, 109, 155, 68, 49, 59, 63, 98, 49, 112, 92, 234, 90, 2, 17, 0, 0, 0, 12, 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