Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1bf7596a4ff70c2af12f95af1f7befc8a1e0c7e280ee6232d645380d97e94e5

Tx prefix hash: 12b3b6d460520260c70fcf734201a502de7db460cf540f8ed821a5f01f8c9dd9
Tx public key: 76aadecd5ae9f4032a3e81a02ad0edb04defe7f4902365bda9ef361d75f69cdb
Timestamp: 1710042258 Timestamp [UCT]: 2024-03-10 03:44:18 Age [y:d:h:m:s]: 01:266:23:00:17
Block: 975008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449534 RingCT/type: yes/0
Extra: 0176aadecd5ae9f4032a3e81a02ad0edb04defe7f4902365bda9ef361d75f69cdb02110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f47861d2d68ce87a29b3d2a94b8bfec6ff3f41907750d99addd5f9e87c41509c 0.600000000000 1434977 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": 975018, "vin": [ { "gen": { "height": 975008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f47861d2d68ce87a29b3d2a94b8bfec6ff3f41907750d99addd5f9e87c41509c" } } ], "extra": [ 1, 118, 170, 222, 205, 90, 233, 244, 3, 42, 62, 129, 160, 42, 208, 237, 176, 77, 239, 231, 244, 144, 35, 101, 189, 169, 239, 54, 29, 117, 246, 156, 219, 2, 17, 0, 0, 0, 12, 0, 17, 5, 91, 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