Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54ffe4dbde2a9ea36f6280e2b16c038454a1029198524339ca1d0d5db5b50d4f

Tx prefix hash: 0617ce30d7e5e08423b6749b6ee38bfa7f32d95fb4ee38b4102a933d4de15bd6
Tx public key: 0fe1927a150bf40729c256cbebe9f3f858371878ca67dbff00cb58a5c5098df8
Timestamp: 1699675811 Timestamp [UCT]: 2023-11-11 04:10:11 Age [y:d:h:m:s]: 01:127:08:00:06
Block: 889058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352206 RingCT/type: yes/0
Extra: 010fe1927a150bf40729c256cbebe9f3f858371878ca67dbff00cb58a5c5098df802110000000233af99f4000000000000000000

1 output(s) for total of 0.695315290000 dcy

stealth address amount amount idx
00: 89561a2bc9e9f87aed3484769b20a621410da2914c9ae4d799300c2ead39acfa 0.695315290000 1345035 of 0

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": 889068, "vin": [ { "gen": { "height": 889058 } } ], "vout": [ { "amount": 695315290, "target": { "key": "89561a2bc9e9f87aed3484769b20a621410da2914c9ae4d799300c2ead39acfa" } } ], "extra": [ 1, 15, 225, 146, 122, 21, 11, 244, 7, 41, 194, 86, 203, 235, 233, 243, 248, 88, 55, 24, 120, 202, 103, 219, 255, 0, 203, 88, 165, 197, 9, 141, 248, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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