Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f77b4698480e2403e99c3a47995529a84aaf287e593d51e46af77f72fe0340ee

Tx prefix hash: a2d93429be7cde98426477e9f6bd7e66c6fa3886002c8fd4f442614bc0cbe2dc
Tx public key: 453a74ffaed5b3c43bba58d4edc8d3dd3fd2a31d42abd244b0d14c82de4eff64
Timestamp: 1724813904 Timestamp [UCT]: 2024-08-28 02:58:24 Age [y:d:h:m:s]: 00:232:16:24:30
Block: 1097457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166159 RingCT/type: yes/0
Extra: 01453a74ffaed5b3c43bba58d4edc8d3dd3fd2a31d42abd244b0d14c82de4eff6402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 528f799fc8a7a3ad8f94ebc967a2e461765975af271ad0a27384d358e498b844 0.600000000000 1572854 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": 1097467, "vin": [ { "gen": { "height": 1097457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "528f799fc8a7a3ad8f94ebc967a2e461765975af271ad0a27384d358e498b844" } } ], "extra": [ 1, 69, 58, 116, 255, 174, 213, 179, 196, 59, 186, 88, 212, 237, 200, 211, 221, 63, 210, 163, 29, 66, 171, 210, 68, 176, 209, 76, 130, 222, 78, 255, 100, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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