Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 614ec5e532dc10eeec61adaabc915bb1e3c4c37f9961654eb7908a08d5387d62

Tx prefix hash: 472eb1c30701e21c8f0f3e323d00165393435a234ccfbc7372ef2eabd2ee1dd3
Tx public key: 4a688bfa3baab02841164f9e299e763a0f28565a3d7575084bf481a0f7187c5a
Timestamp: 1715081660 Timestamp [UCT]: 2024-05-07 11:34:20 Age [y:d:h:m:s]: 01:270:21:36:27
Block: 1016788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452156 RingCT/type: yes/0
Extra: 014a688bfa3baab02841164f9e299e763a0f28565a3d7575084bf481a0f7187c5a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 706709310ba4ec9089cb9d3517bf1f0d4426d78ad421aae6c46ca6ec857a3147 0.600000000000 1480471 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": 1016798, "vin": [ { "gen": { "height": 1016788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "706709310ba4ec9089cb9d3517bf1f0d4426d78ad421aae6c46ca6ec857a3147" } } ], "extra": [ 1, 74, 104, 139, 250, 59, 170, 176, 40, 65, 22, 79, 158, 41, 158, 118, 58, 15, 40, 86, 90, 61, 117, 117, 8, 75, 244, 129, 160, 247, 24, 124, 90, 2, 17, 0, 0, 0, 1, 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