Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe6b0293a8444c4029974a3490cd98a05bc2eabd2c23237e836aa9baae37cea6

Tx prefix hash: f0748ae06fe804a0d7b644c9a4e902be7ebeefde2c7e5fea67ae0964a56cb5be
Tx public key: 957bfc88a9dd3e74e61e3dad067d81bee8a2dccddca331da7f143382839a8672
Timestamp: 1696625193 Timestamp [UCT]: 2023-10-06 20:46:33 Age [y:d:h:m:s]: 01:255:13:30:41
Block: 863980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443605 RingCT/type: yes/0
Extra: 01957bfc88a9dd3e74e61e3dad067d81bee8a2dccddca331da7f143382839a86720211000000054b8f5122000000000000000000

1 output(s) for total of 0.841929334000 dcy

stealth address amount amount idx
00: 1c3cd9d7e81c2359f0ed1cd4b4c14a59c66d8e620a5341a855aede25d6fc9297 0.841929334000 1318484 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": 863990, "vin": [ { "gen": { "height": 863980 } } ], "vout": [ { "amount": 841929334, "target": { "key": "1c3cd9d7e81c2359f0ed1cd4b4c14a59c66d8e620a5341a855aede25d6fc9297" } } ], "extra": [ 1, 149, 123, 252, 136, 169, 221, 62, 116, 230, 30, 61, 173, 6, 125, 129, 190, 232, 162, 220, 205, 220, 163, 49, 218, 127, 20, 51, 130, 131, 154, 134, 114, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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