Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966483a3ee881b967043a695719dad6031ee32932b41ef782046950d30a254af

Tx prefix hash: 2785bcfc8f78d83911b151df0e8c935b8cb6ddd4086a33681ca304c2a2f174c1
Tx public key: 4a7e6774b7db35b0d2967d7fa184214bc50148966098b5cc406d5d5dcd7cbe0e
Timestamp: 1728749269 Timestamp [UCT]: 2024-10-12 16:07:49 Age [y:d:h:m:s]: 00:173:09:50:50
Block: 1130089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123712 RingCT/type: yes/0
Extra: 014a7e6774b7db35b0d2967d7fa184214bc50148966098b5cc406d5d5dcd7cbe0e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d409338b5ce2227e6adee776b178a207cefe5fd7910f8fe49df635f1eee597d0 0.600000000000 1612960 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": 1130099, "vin": [ { "gen": { "height": 1130089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d409338b5ce2227e6adee776b178a207cefe5fd7910f8fe49df635f1eee597d0" } } ], "extra": [ 1, 74, 126, 103, 116, 183, 219, 53, 176, 210, 150, 125, 127, 161, 132, 33, 75, 197, 1, 72, 150, 96, 152, 181, 204, 64, 109, 93, 93, 205, 124, 190, 14, 2, 17, 0, 0, 0, 6, 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