Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb7a8068afdcf5104bd64da9fe2f34fef6eeb54ab6fbced24a4b3bab2fa987d

Tx prefix hash: a9b19e876c359e9bd6f027ff835fa748b7f7d34782633a2025989d391df184eb
Tx public key: f54e96d1bd9f3dffd8043e0f991fba6cf1774c678f8b843b0723280339783bf4
Timestamp: 1719415369 Timestamp [UCT]: 2024-06-26 15:22:49 Age [y:d:h:m:s]: 00:263:21:10:40
Block: 1052698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188573 RingCT/type: yes/0
Extra: 01f54e96d1bd9f3dffd8043e0f991fba6cf1774c678f8b843b0723280339783bf402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b409b230318a4f0985d8e7de87d5ce02e32947a401cd461fc8086c5f8d6dad1 0.600000000000 1523029 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": 1052708, "vin": [ { "gen": { "height": 1052698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b409b230318a4f0985d8e7de87d5ce02e32947a401cd461fc8086c5f8d6dad1" } } ], "extra": [ 1, 245, 78, 150, 209, 189, 159, 61, 255, 216, 4, 62, 15, 153, 31, 186, 108, 241, 119, 76, 103, 143, 139, 132, 59, 7, 35, 40, 3, 57, 120, 59, 244, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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