Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0cbb305d28f8a9af5bf4c53a348631b1764c1df12bc112f0e03572f8d700bcd

Tx prefix hash: f1f6b9d199bb874d2e0026c7b8d0a4bf5d02caf6ae506447b1cca608a97df7db
Tx public key: 031ef379781176a00c31e46a39e76cac14d11f5aa915ee790f547ed0dc62f791
Timestamp: 1705636830 Timestamp [UCT]: 2024-01-19 04:00:30 Age [y:d:h:m:s]: 01:294:03:54:43
Block: 938454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469059 RingCT/type: yes/0
Extra: 01031ef379781176a00c31e46a39e76cac14d11f5aa915ee790f547ed0dc62f7910211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86b3e2350e26cdc45032ed41215582971e9996bdf763914e3b17616e80d18cef 0.600000000000 1396524 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": 938464, "vin": [ { "gen": { "height": 938454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86b3e2350e26cdc45032ed41215582971e9996bdf763914e3b17616e80d18cef" } } ], "extra": [ 1, 3, 30, 243, 121, 120, 17, 118, 160, 12, 49, 228, 106, 57, 231, 108, 172, 20, 209, 31, 90, 169, 21, 238, 121, 15, 84, 126, 208, 220, 98, 247, 145, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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