Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0769e3ba27d30fba10abcf2a8c09a0eb65c3fe2911723976aff93dada20d245

Tx prefix hash: be20ee9b08700e1ae8196053973dcbefcb2077f215fdb86d955d8cb28b00e086
Tx public key: a298698c632f28a954a0d7015ef0a5efd5ddd1e6ff78c9f0d5b209191b946654
Timestamp: 1728551955 Timestamp [UCT]: 2024-10-10 09:19:15 Age [y:d:h:m:s]: 01:029:12:10:30
Block: 1128457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279458 RingCT/type: yes/0
Extra: 01a298698c632f28a954a0d7015ef0a5efd5ddd1e6ff78c9f0d5b209191b946654021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10b26d5f2d1e007111b96456a967c818072b650482e55fc88daeb1e3b81f57e2 0.600000000000 1611276 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": 1128467, "vin": [ { "gen": { "height": 1128457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10b26d5f2d1e007111b96456a967c818072b650482e55fc88daeb1e3b81f57e2" } } ], "extra": [ 1, 162, 152, 105, 140, 99, 47, 40, 169, 84, 160, 215, 1, 94, 240, 165, 239, 213, 221, 209, 230, 255, 120, 201, 240, 213, 178, 9, 25, 27, 148, 102, 84, 2, 17, 0, 0, 0, 2, 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