Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72efb9579e5ed518946f3ae768a8b3a52f53a3ccc5c5f6caf531fd57d38bfad

Tx prefix hash: 0e444fc9d6f4ad406a7d7fc5cd7d50a8ceba9e831c5328d908412c8ee3478ee5
Tx public key: 4490d983fb0b1785dfe9ffa631ddae364516164c6895ef655399a57491242fbc
Timestamp: 1713070443 Timestamp [UCT]: 2024-04-14 04:54:03 Age [y:d:h:m:s]: 01:200:11:45:37
Block: 1000084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401970 RingCT/type: yes/0
Extra: 014490d983fb0b1785dfe9ffa631ddae364516164c6895ef655399a57491242fbc0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0295fbc2e8393c6f5deef41c272a96f8294e1770a60d1ec55e72e5cbe519e93 0.600000000000 1460574 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": 1000094, "vin": [ { "gen": { "height": 1000084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0295fbc2e8393c6f5deef41c272a96f8294e1770a60d1ec55e72e5cbe519e93" } } ], "extra": [ 1, 68, 144, 217, 131, 251, 11, 23, 133, 223, 233, 255, 166, 49, 221, 174, 54, 69, 22, 22, 76, 104, 149, 239, 101, 83, 153, 165, 116, 145, 36, 47, 188, 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