Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ee804d22821d262b1cab7ac155aaaf82a31341c6df98667ac438ec0ce0dc107

Tx prefix hash: 50aa45e14ec4d43b5b42a879d4ec0fd8db99880a6d0b750ee419ae19817a602d
Tx public key: 107cc459fb558eb8a70ad9d893f0f3ef01f4b82c1bfa745f546d23651614a8ba
Timestamp: 1723286132 Timestamp [UCT]: 2024-08-10 10:35:32 Age [y:d:h:m:s]: 00:292:06:01:36
Block: 1084809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208795 RingCT/type: yes/0
Extra: 01107cc459fb558eb8a70ad9d893f0f3ef01f4b82c1bfa745f546d23651614a8ba021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 730f2628ea475c06e26b1e93829242a8661ab60e840e82a7c670a1633050c9e5 0.600000000000 1559216 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": 1084819, "vin": [ { "gen": { "height": 1084809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "730f2628ea475c06e26b1e93829242a8661ab60e840e82a7c670a1633050c9e5" } } ], "extra": [ 1, 16, 124, 196, 89, 251, 85, 142, 184, 167, 10, 217, 216, 147, 240, 243, 239, 1, 244, 184, 44, 27, 250, 116, 95, 84, 109, 35, 101, 22, 20, 168, 186, 2, 17, 0, 0, 0, 8, 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