Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 171ef7d5cebd3ec77614f2afc0d6a91b535b3bcd811ea3b90e82ff69118fb350

Tx prefix hash: c1763d3367cb46664feb407c54459f20260e2f0104a19998f01b01ff231abc44
Tx public key: fb5532d2132b954b494ad360f0c2deb87db3d0a6a6ceabdb3c234eaf8be6337a
Timestamp: 1704436744 Timestamp [UCT]: 2024-01-05 06:39:04 Age [y:d:h:m:s]: 01:004:13:40:10
Block: 928507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264606 RingCT/type: yes/0
Extra: 01fb5532d2132b954b494ad360f0c2deb87db3d0a6a6ceabdb3c234eaf8be6337a02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e8334fff777e08d1a1dfa3dbbd87f8329d68ad7871cce2f9b55a6b5fbc708ff 0.600000000000 1386367 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": 928517, "vin": [ { "gen": { "height": 928507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e8334fff777e08d1a1dfa3dbbd87f8329d68ad7871cce2f9b55a6b5fbc708ff" } } ], "extra": [ 1, 251, 85, 50, 210, 19, 43, 149, 75, 73, 74, 211, 96, 240, 194, 222, 184, 125, 179, 208, 166, 166, 206, 171, 219, 60, 35, 78, 175, 139, 230, 51, 122, 2, 17, 0, 0, 0, 4, 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