Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3f16e1f8bea190e827e0c3cf7c0745f287eb3e30b9f8d6e595c958191f68680

Tx prefix hash: c361e405be6017b85daf860696faa84f4a54dde630c2a76db80a261f1ae1e8a7
Tx public key: 0769277b3357af368d723e30cceb2eb23a1874ac6526645241f4ae831c954142
Timestamp: 1723834656 Timestamp [UCT]: 2024-08-16 18:57:36 Age [y:d:h:m:s]: 00:266:01:30:08
Block: 1089347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190048 RingCT/type: yes/0
Extra: 010769277b3357af368d723e30cceb2eb23a1874ac6526645241f4ae831c95414202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32a0edaa8d0a6ee2ac99edda6b2116913b0c896be2d788ccd0d0a08bbbd01f54 0.600000000000 1563966 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": 1089357, "vin": [ { "gen": { "height": 1089347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32a0edaa8d0a6ee2ac99edda6b2116913b0c896be2d788ccd0d0a08bbbd01f54" } } ], "extra": [ 1, 7, 105, 39, 123, 51, 87, 175, 54, 141, 114, 62, 48, 204, 235, 46, 178, 58, 24, 116, 172, 101, 38, 100, 82, 65, 244, 174, 131, 28, 149, 65, 66, 2, 17, 0, 0, 0, 7, 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