Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 716670d9d2d67f9faf09240c7732be83607afd5913d6ea47155eeae2225286a1

Tx prefix hash: f9c7f6aa4ff1fbcf511445ea0f56a3df22c7fabe33d0ced6f6d00e4dd85244a9
Tx public key: a9f8ae1d8ed9c7e3011b4d10fd3d2474919f793d70eb2d5cc56d850c7d13342e
Timestamp: 1705669248 Timestamp [UCT]: 2024-01-19 13:00:48 Age [y:d:h:m:s]: 01:087:17:32:56
Block: 938716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323814 RingCT/type: yes/0
Extra: 01a9f8ae1d8ed9c7e3011b4d10fd3d2474919f793d70eb2d5cc56d850c7d13342e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cfef09818d1774507615dc83cb154b0eae287cefcb801321b23a4dd0a15abba 0.600000000000 1396792 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": 938726, "vin": [ { "gen": { "height": 938716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cfef09818d1774507615dc83cb154b0eae287cefcb801321b23a4dd0a15abba" } } ], "extra": [ 1, 169, 248, 174, 29, 142, 217, 199, 227, 1, 27, 77, 16, 253, 61, 36, 116, 145, 159, 121, 61, 112, 235, 45, 92, 197, 109, 133, 12, 125, 19, 52, 46, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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