Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e73cd1e046d6c95a684fa7ddf7fa5d200c3fd474b5eebcf36f5a8ddebf603be

Tx prefix hash: d95fafc84132d596c6cf83ac71abb33a0cae5909852c6fab239780dcd07684fd
Tx public key: 6de29fb9f5cbe46862205025f5406332331a919991c39658841e1cb8c17c59fd
Timestamp: 1722799310 Timestamp [UCT]: 2024-08-04 19:21:50 Age [y:d:h:m:s]: 00:171:14:00:01
Block: 1080760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122709 RingCT/type: yes/0
Extra: 016de29fb9f5cbe46862205025f5406332331a919991c39658841e1cb8c17c59fd02110000001de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78f5c3b1c328b9313d9294e05c8c8f63e5eba2d6929eeb67cc50533489699d0e 0.600000000000 1554241 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": 1080770, "vin": [ { "gen": { "height": 1080760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78f5c3b1c328b9313d9294e05c8c8f63e5eba2d6929eeb67cc50533489699d0e" } } ], "extra": [ 1, 109, 226, 159, 185, 245, 203, 228, 104, 98, 32, 80, 37, 245, 64, 99, 50, 51, 26, 145, 153, 145, 195, 150, 88, 132, 30, 28, 184, 193, 124, 89, 253, 2, 17, 0, 0, 0, 29, 233, 20, 221, 21, 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