Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5eb7c9e58be3d8e3e939e94c71f77f5b0341eb3dc8f4ec25f9400578811aa6ae

Tx prefix hash: 0f8ea9efd3e4648a83e6c4fdbd67e3af6f8974b0e4cb2f5aa1ed241e8a40858c
Tx public key: 0ad6fd5fe94b5a61190ac739b9531766e6c4e43529defdf813c7d272baeeff69
Timestamp: 1723560217 Timestamp [UCT]: 2024-08-13 14:43:37 Age [y:d:h:m:s]: 01:086:11:25:47
Block: 1087077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320261 RingCT/type: yes/0
Extra: 010ad6fd5fe94b5a61190ac739b9531766e6c4e43529defdf813c7d272baeeff69021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a08bdd8bba61dea832ba0d507cfa81e2ce21d3a8225d828635441998efc6dfbe 0.600000000000 1561682 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": 1087087, "vin": [ { "gen": { "height": 1087077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a08bdd8bba61dea832ba0d507cfa81e2ce21d3a8225d828635441998efc6dfbe" } } ], "extra": [ 1, 10, 214, 253, 95, 233, 75, 90, 97, 25, 10, 199, 57, 185, 83, 23, 102, 230, 196, 228, 53, 41, 222, 253, 248, 19, 199, 210, 114, 186, 238, 255, 105, 2, 17, 0, 0, 0, 6, 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