Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6afbf3251509096f94aabef2aad2b97901e929a5f057d778669b2cc4a479bd26

Tx prefix hash: 21b19a28e77413d2a0c80585d87c999f207d6745ae12df2097bbd327c27f5e0a
Tx public key: 4e03a755b3ddf623f23192ebf5f2514c84712f623d017bbbc8977b1e0c9f8bc2
Timestamp: 1709766180 Timestamp [UCT]: 2024-03-06 23:03:00 Age [y:d:h:m:s]: 01:103:10:25:46
Block: 972716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334854 RingCT/type: yes/0
Extra: 014e03a755b3ddf623f23192ebf5f2514c84712f623d017bbbc8977b1e0c9f8bc202110000000646812bb8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f39403856618200926525329557b87a4ff64eb091eaa73b09c6161e5cda3feef 0.600000000000 1432635 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": 972726, "vin": [ { "gen": { "height": 972716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f39403856618200926525329557b87a4ff64eb091eaa73b09c6161e5cda3feef" } } ], "extra": [ 1, 78, 3, 167, 85, 179, 221, 246, 35, 242, 49, 146, 235, 245, 242, 81, 76, 132, 113, 47, 98, 61, 1, 123, 187, 200, 151, 123, 30, 12, 159, 139, 194, 2, 17, 0, 0, 0, 6, 70, 129, 43, 184, 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