Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d43348904c23d439ed1478bc88758c404f9af64c9d0caf97967117a4e661c4b8

Tx prefix hash: f1b68f2c3f736c3810f234fd1f89e50d80a40db57edf66bd4675d81859c8b6a3
Tx public key: 038d09cbe727c4bd2cfeb2677168a28f8ddcc7361325c096a7b321a525a4ee68
Timestamp: 1686539019 Timestamp [UCT]: 2023-06-12 03:03:39 Age [y:d:h:m:s]: 01:304:00:37:16
Block: 780408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478464 RingCT/type: yes/0
Extra: 01038d09cbe727c4bd2cfeb2677168a28f8ddcc7361325c096a7b321a525a4ee68021100000002faf35c9c000000000000000000

1 output(s) for total of 1.592885254000 dcy

stealth address amount amount idx
00: 1af674cf4d616dff865080f963065fd44ba5a4600462c8ca59f570eb112479ef 1.592885254000 1230111 of 0

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": 780418, "vin": [ { "gen": { "height": 780408 } } ], "vout": [ { "amount": 1592885254, "target": { "key": "1af674cf4d616dff865080f963065fd44ba5a4600462c8ca59f570eb112479ef" } } ], "extra": [ 1, 3, 141, 9, 203, 231, 39, 196, 189, 44, 254, 178, 103, 113, 104, 162, 143, 141, 220, 199, 54, 19, 37, 192, 150, 167, 179, 33, 165, 37, 164, 238, 104, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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