Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5649d687df8a4f1fadde192750bbf11a576fa5560b1158c279315881213f6118

Tx prefix hash: c8ae0595173d8685e8322cbd005bbc92f89231d5857c4f71e68b9f1d57c35481
Tx public key: e5e6e42640a0bef43f9159a501b3cf7036e0fcf37c3cd880e67f9a30195b4cad
Timestamp: 1696575348 Timestamp [UCT]: 2023-10-06 06:55:48 Age [y:d:h:m:s]: 01:147:00:37:48
Block: 863548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366103 RingCT/type: yes/0
Extra: 01e5e6e42640a0bef43f9159a501b3cf7036e0fcf37c3cd880e67f9a30195b4cad02110000000133af99f4000000000000000000

1 output(s) for total of 0.844708836000 dcy

stealth address amount amount idx
00: 8fd5410fcc27d626a753e03607d9a92f83629cd7350035cce37a088efbe16217 0.844708836000 1318006 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": 863558, "vin": [ { "gen": { "height": 863548 } } ], "vout": [ { "amount": 844708836, "target": { "key": "8fd5410fcc27d626a753e03607d9a92f83629cd7350035cce37a088efbe16217" } } ], "extra": [ 1, 229, 230, 228, 38, 64, 160, 190, 244, 63, 145, 89, 165, 1, 179, 207, 112, 54, 224, 252, 243, 124, 60, 216, 128, 230, 127, 154, 48, 25, 91, 76, 173, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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