Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b433cb8ba3048ea177dc843c56388f84089c2b8e669d06aafaf060da41d0f33e

Tx prefix hash: a22f7eab9c6cf69230cb3aea5165a738bae9c79dc50fd25dcad527b7df117153
Tx public key: e851fdc81ca2ce06c39044ef12e210335d51ec5e3e05e7e0cd18de9889f269a2
Timestamp: 1721345728 Timestamp [UCT]: 2024-07-18 23:35:28 Age [y:d:h:m:s]: 00:263:02:12:46
Block: 1068724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187925 RingCT/type: yes/0
Extra: 01e851fdc81ca2ce06c39044ef12e210335d51ec5e3e05e7e0cd18de9889f269a2021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a08a27c5f94f2b10219f020be4dcbcf513725259c4493078704e3413672ec57d 0.600000000000 1539865 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": 1068734, "vin": [ { "gen": { "height": 1068724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a08a27c5f94f2b10219f020be4dcbcf513725259c4493078704e3413672ec57d" } } ], "extra": [ 1, 232, 81, 253, 200, 28, 162, 206, 6, 195, 144, 68, 239, 18, 226, 16, 51, 93, 81, 236, 94, 62, 5, 231, 224, 205, 24, 222, 152, 137, 242, 105, 162, 2, 17, 0, 0, 0, 3, 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