Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e34943eb028f6afbb6f8c07cbb4f8fdde347b3139ce747dda15214528cda25f

Tx prefix hash: 8f3b4a16d878a440b1cc9a5d601bc3f883dec9e4187ef7be80ddc1cae0a65ae7
Tx public key: 75512d87f1ae8517a3f989bf6a3ffffca78195478e70a5b4211e7b3254573d25
Timestamp: 1706017329 Timestamp [UCT]: 2024-01-23 13:42:09 Age [y:d:h:m:s]: 01:084:14:28:15
Block: 941604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321564 RingCT/type: yes/0
Extra: 0175512d87f1ae8517a3f989bf6a3ffffca78195478e70a5b4211e7b3254573d2502110000001952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da638021a6e7c83e4f0d0739ec8d1774de1b7d8adb2e7e116e9754d470cb8961 0.600000000000 1399760 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": 941614, "vin": [ { "gen": { "height": 941604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da638021a6e7c83e4f0d0739ec8d1774de1b7d8adb2e7e116e9754d470cb8961" } } ], "extra": [ 1, 117, 81, 45, 135, 241, 174, 133, 23, 163, 249, 137, 191, 106, 63, 255, 252, 167, 129, 149, 71, 142, 112, 165, 180, 33, 30, 123, 50, 84, 87, 61, 37, 2, 17, 0, 0, 0, 25, 82, 212, 126, 148, 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