Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ba15961bc6011888ff424375bef091f3a7e6585bbef32bfde9434e2e9b6a758

Tx prefix hash: 4aff4c74c6a9b02c308c14ed8a6cbc7a6dea1f0afd3d1d7a2fb6cf8adc87e653
Tx public key: 52e564583f733d186beffef41baecd9ed3b536a46800ad23ecdce31742dea129
Timestamp: 1658867465 Timestamp [UCT]: 2022-07-26 20:31:05 Age [y:d:h:m:s]: 02:301:12:03:50
Block: 552348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 736724 RingCT/type: yes/0
Extra: 0152e564583f733d186beffef41baecd9ed3b536a46800ad23ecdce31742dea129021100000002faf35c9c000000000000000000

1 output(s) for total of 9.074901383000 dcy

stealth address amount amount idx
00: 28e35677c3296f26d8cb63063db7e3a0bfa0cddcb444308f2f52e452f2038982 9.074901383000 984046 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": 552358, "vin": [ { "gen": { "height": 552348 } } ], "vout": [ { "amount": 9074901383, "target": { "key": "28e35677c3296f26d8cb63063db7e3a0bfa0cddcb444308f2f52e452f2038982" } } ], "extra": [ 1, 82, 229, 100, 88, 63, 115, 61, 24, 107, 239, 254, 244, 27, 174, 205, 158, 211, 181, 54, 164, 104, 0, 173, 35, 236, 220, 227, 23, 66, 222, 161, 41, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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