Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6033c39073ae1bcccdbf5d0f44af1ec323bd2e0c35efd8e87a423f8eb0561d38

Tx prefix hash: 4f3eee12061f2ef8003df2ee6162505ebeb2c10096c350887f920a6e0faf22b9
Tx public key: 4a2e19844d2edda0ec867af8bf29c2dafe050105c38dbd4d8c52ca1da9733ce4
Timestamp: 1707207726 Timestamp [UCT]: 2024-02-06 08:22:06 Age [y:d:h:m:s]: 01:023:02:38:37
Block: 951493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277540 RingCT/type: yes/0
Extra: 014a2e19844d2edda0ec867af8bf29c2dafe050105c38dbd4d8c52ca1da9733ce40211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 043f863c18e1d8a3f858da27dd2c669811b11577bbef2d262e33038b369ee8b3 0.600000000000 1410263 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": 951503, "vin": [ { "gen": { "height": 951493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "043f863c18e1d8a3f858da27dd2c669811b11577bbef2d262e33038b369ee8b3" } } ], "extra": [ 1, 74, 46, 25, 132, 77, 46, 221, 160, 236, 134, 122, 248, 191, 41, 194, 218, 254, 5, 1, 5, 195, 141, 189, 77, 140, 82, 202, 29, 169, 115, 60, 228, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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