Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7efe3c7d66d55a26b4109c0378f2cf914d81935b5e8b45e714fba58ba22c46ae

Tx prefix hash: 90f516efa046019a59a5ccf84501094b31bd14d1abd67b0a7e84feaec6532b1b
Tx public key: 3d860e0a25fa27096f47b8785ff08628605b570f57503496696883ac3c905f06
Timestamp: 1710679964 Timestamp [UCT]: 2024-03-17 12:52:44 Age [y:d:h:m:s]: 00:188:02:26:54
Block: 980305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134726 RingCT/type: yes/0
Extra: 013d860e0a25fa27096f47b8785ff08628605b570f57503496696883ac3c905f0602110000001459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f19f9bc7f86c7e08a06cf6631fc77532f0db90fe8743ed6fd6fb3822b8e73076 0.600000000000 1440370 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": 980315, "vin": [ { "gen": { "height": 980305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f19f9bc7f86c7e08a06cf6631fc77532f0db90fe8743ed6fd6fb3822b8e73076" } } ], "extra": [ 1, 61, 134, 14, 10, 37, 250, 39, 9, 111, 71, 184, 120, 95, 240, 134, 40, 96, 91, 87, 15, 87, 80, 52, 150, 105, 104, 131, 172, 60, 144, 95, 6, 2, 17, 0, 0, 0, 20, 89, 218, 211, 245, 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