Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96e4148cfcb27b444374e5d6df02f9cc9a391037f9ed2645c723ca55bc69fd06

Tx prefix hash: d82f6644da810044b62f51d780655c0388b7d2dc5c448d90b5500caa06bb3d06
Tx public key: 0cacc1f11741887b79bbe6f58b32c290fedc3ccd3b63a9f3289b1e04163032f8
Timestamp: 1714083287 Timestamp [UCT]: 2024-04-25 22:14:47 Age [y:d:h:m:s]: 00:245:18:21:29
Block: 1008495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175914 RingCT/type: yes/0
Extra: 010cacc1f11741887b79bbe6f58b32c290fedc3ccd3b63a9f3289b1e04163032f802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d445389418559186ca4c5ef0b3ee5a198f81fb3f1ea88e60381a09c538860e37 0.600000000000 1469965 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": 1008505, "vin": [ { "gen": { "height": 1008495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d445389418559186ca4c5ef0b3ee5a198f81fb3f1ea88e60381a09c538860e37" } } ], "extra": [ 1, 12, 172, 193, 241, 23, 65, 136, 123, 121, 187, 230, 245, 139, 50, 194, 144, 254, 220, 60, 205, 59, 99, 169, 243, 40, 155, 30, 4, 22, 48, 50, 248, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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