Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e8d47e341891613d7f8bae40458002b409acb86b6f513a32342a40b797d8000

Tx prefix hash: cc7da1736f1c8dc2ace1e69b4fde928c2f242919128ef75ea6e06c877bd04457
Tx public key: d9642459f58de7cabdade22cae086a39e620f4a07bef909a1f9551e1f011eb81
Timestamp: 1763023810 Timestamp [UCT]: 2025-11-13 08:50:10 Age [y:d:h:m:s]: 00:051:21:18:56
Block: 1411123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37161 RingCT/type: yes/0
Extra: 01d9642459f58de7cabdade22cae086a39e620f4a07bef909a1f9551e1f011eb81021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1779c8470feccb0bb0f3ec3514cb764daecff0f1a70dc13c076809fbe96d5c6 0.600000000000 1899580 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": 1411133, "vin": [ { "gen": { "height": 1411123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1779c8470feccb0bb0f3ec3514cb764daecff0f1a70dc13c076809fbe96d5c6" } } ], "extra": [ 1, 217, 100, 36, 89, 245, 141, 231, 202, 189, 173, 226, 44, 174, 8, 106, 57, 230, 32, 244, 160, 123, 239, 144, 154, 31, 149, 81, 225, 240, 17, 235, 129, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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