Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08b74ece3a13d7baf8eaec540979a7996893a6a01562ce302e0754705e105fb2

Tx prefix hash: a27b90e01f31b4865f109b9c85f5824898e54b13a7e6a29e2e4823988ea932b3
Tx public key: a828d0944e05a7b50027f7a609bc9f0a4d591e1d0bdb52ea464f9562ae64bdcc
Timestamp: 1710516305 Timestamp [UCT]: 2024-03-15 15:25:05 Age [y:d:h:m:s]: 01:041:22:54:31
Block: 978946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290977 RingCT/type: yes/0
Extra: 01a828d0944e05a7b50027f7a609bc9f0a4d591e1d0bdb52ea464f9562ae64bdcc02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80c0495f369ef2569592bd3b4d9fca579182a26d0c36eb281de13335923666a1 0.600000000000 1438975 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": 978956, "vin": [ { "gen": { "height": 978946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80c0495f369ef2569592bd3b4d9fca579182a26d0c36eb281de13335923666a1" } } ], "extra": [ 1, 168, 40, 208, 148, 78, 5, 167, 181, 0, 39, 247, 166, 9, 188, 159, 10, 77, 89, 30, 29, 11, 219, 82, 234, 70, 79, 149, 98, 174, 100, 189, 204, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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