Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae9b7312cd1119e184f5c04b1a03ee264a4cb7663a26e64050542d3db318bc07

Tx prefix hash: f77e17e98c21b837696a38ad462742b038a22aae081b8d885e9ec75cd888da73
Tx public key: d4c73754bdb6d8ec57a9dc5b710ea6be8ca7be9020d5cceb5b16ca2f6511287d
Timestamp: 1703578283 Timestamp [UCT]: 2023-12-26 08:11:23 Age [y:d:h:m:s]: 01:316:17:41:11
Block: 921412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485194 RingCT/type: yes/0
Extra: 01d4c73754bdb6d8ec57a9dc5b710ea6be8ca7be9020d5cceb5b16ca2f6511287d02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82d4a8a3cce767ee0217de9d902c9e3239484944b152fa93c0874bacb41c84a1 0.600000000000 1379100 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": 921422, "vin": [ { "gen": { "height": 921412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82d4a8a3cce767ee0217de9d902c9e3239484944b152fa93c0874bacb41c84a1" } } ], "extra": [ 1, 212, 199, 55, 84, 189, 182, 216, 236, 87, 169, 220, 91, 113, 14, 166, 190, 140, 167, 190, 144, 32, 213, 204, 235, 91, 22, 202, 47, 101, 17, 40, 125, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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