Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 896e7e997c24cbd9c97c3de58e71853d6e7d6b1ded2b35d75b87491db23d7df3

Tx prefix hash: fafd07f6600ba4765f72646166aba8d81b13ed4f3b8726056aad0c94a84e8671
Tx public key: 3c3e7bcf2627932f0331f25a4483f3369610fb7939eb57b90a57c3dbefadc12e
Timestamp: 1716798171 Timestamp [UCT]: 2024-05-27 08:22:51 Age [y:d:h:m:s]: 00:293:20:35:37
Block: 1031028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210013 RingCT/type: yes/0
Extra: 013c3e7bcf2627932f0331f25a4483f3369610fb7939eb57b90a57c3dbefadc12e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfe1ee9e75e58d41fd041a405195e1bb7cc7b8b6d80414adde1e7390a06aaa8a 0.600000000000 1499371 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": 1031038, "vin": [ { "gen": { "height": 1031028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfe1ee9e75e58d41fd041a405195e1bb7cc7b8b6d80414adde1e7390a06aaa8a" } } ], "extra": [ 1, 60, 62, 123, 207, 38, 39, 147, 47, 3, 49, 242, 90, 68, 131, 243, 54, 150, 16, 251, 121, 57, 235, 87, 185, 10, 87, 195, 219, 239, 173, 193, 46, 2, 17, 0, 0, 0, 1, 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