Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50628142696fb56e081cb8bf1bb8034de849a6565898cc13a47265049071d353

Tx prefix hash: 9b68ca4d15f99ce784677c14d71112a6a61da604ef44934b7c6351340fc21d43
Tx public key: 8661cec2eb93b7a31d0d08816b0593b012e535ddcf2c8a7f15aba7b19a77f8a2
Timestamp: 1585735370 Timestamp [UCT]: 2020-04-01 10:02:50 Age [y:d:h:m:s]: 04:307:09:35:52
Block: 90784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119202 RingCT/type: yes/0
Extra: 018661cec2eb93b7a31d0d08816b0593b012e535ddcf2c8a7f15aba7b19a77f8a202110000000186362411000000000000000000

1 output(s) for total of 307.040522127000 dcy

stealth address amount amount idx
00: f1068c11fb9acddb4b0f90e9375b1a6e1e99023e2da907e1e917f97944d220dd 307.040522127000 162490 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": 90794, "vin": [ { "gen": { "height": 90784 } } ], "vout": [ { "amount": 307040522127, "target": { "key": "f1068c11fb9acddb4b0f90e9375b1a6e1e99023e2da907e1e917f97944d220dd" } } ], "extra": [ 1, 134, 97, 206, 194, 235, 147, 183, 163, 29, 13, 8, 129, 107, 5, 147, 176, 18, 229, 53, 221, 207, 44, 138, 127, 21, 171, 167, 177, 154, 119, 248, 162, 2, 17, 0, 0, 0, 1, 134, 54, 36, 17, 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